home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
NetNews Offline 2
/
NetNews Offline Volume 2.iso
/
news
/
de
/
comm
/
isdn
/
4141
< prev
next >
Wrap
Internet Message Format
|
1996-08-06
|
2KB
Path: rzstud2.rz.uni-karlsruhe.de!un7j
From: un7j@rzstud2.rz.uni-karlsruhe.de (Hans-Joerg Fischer)
Newsgroups: de.comm.isdn
Subject: S: Help on isdn4linux problem
Date: 22 Feb 1996 11:55:03 GMT
Organization: University of Karlsruhe, Germany
Message-ID: <4ghlin$ofn@nz12.rz.uni-karlsruhe.de>
NNTP-Posting-Host: rzstud2.rz.uni-karlsruhe.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
NNTP-Posting-User: un7j
X-Newsreader: TIN [version 1.2 PL2]
Hi!
The following problem occured with the isdn4linux driver package:
Hardware: 486/66, 16 MB RAM
blablabla
Teles 16.3 ISA/ISDN Card
E-DSS1
Software: Linux Kernel V 1.2.6
Linux Kernel V 1.2.13
Linux Modules V 1.2.8
isdn4linux V 0.9g
After applying the 16.3 patch on the isdn4linux sources and successfully
compiling them, the
insmod isdn.o
command works, but
insmod teles.o io=0xd0000,0x10,0x180
bombs the first time. Unloading the modules with rmmod and reloading it with
a different interrupt number (it cannot get the same interrupt any more...)
then seems (!) to work.
However, even though I set the MSN correctly, I always get a BUSY (using
minicom with terminal emulation) resp. the card immidiatly hangs up again
while trying to connect to another ISDN host.
So, my questions
1) Why does the driver bombs the first time?
2) Why do I always get a BUSY?
Please eMail.
Thank you for your help.
CU
-JF-
--
_____..---======+*+=======---.._____
___________________ __,-='=====____ ============== _____======
(.__________________I__) - _-=_/ ------=+=-------'
/ /__...---==='---+---_'
'----'---.___ - _ = _.-' Joerg Fischer
-------' Werderstrasse 73
76137 Karlsruhe
~ Joerg.Fischer@stud.uni-karlsruhe.de